home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX 5.3 for Indy R4400
/
IRIX 5.3 for Indy R4400 175MHz.img
/
dist
/
eoe2.idb
/
usr
/
share
/
catman
/
a_man
/
cat1
/
snmpd.z
/
snmpd
Wrap
Text File
|
1995-02-28
|
10KB
|
258 lines
SSSSNNNNMMMMPPPPDDDD((((1111MMMM)))) SSSSNNNNMMMMPPPPDDDD((((1111MMMM))))
NNNNAAAAMMMMEEEE
snmpd - Simple Network Management Protocol daemon
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////eeeettttcccc////ssssnnnnmmmmppppdddd [ ----dddd debug ] [ ----llll loglevel ] [ ----uuuu namelist ]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_s_n_m_p_d is a daemon for the Simple Network Management Protocol (SNMP) as
specified in Internet RFC 1157 and supports MIB II as specified in
Internet RFC 1213. The daemon, called the SNMP agent, can be configured
to run from the network startup script at boot time by the command
_c_h_k_c_o_n_f_i_g _s_n_m_p_d _o_n, or started from the command line. You must be
super-user (root) to run _s_n_m_p_d. _s_n_m_p_d listens on a _u_d_p(7P) socket for
the _s_n_m_p service for SNMP queries. If no such service can be found, a
default port of 161 is used. By default, _s_n_m_p_d logs its messages to
_s_y_s_l_o_g(3B).
_s_n_m_p_d checks that each incoming request is authorized. The file
/_e_t_c/_s_n_m_p_d._a_u_t_h is used to specify sets of hosts and SNMP communities
which have either ggggeeeetttt or sssseeeetttt privileges. Entries in the file have the
form:
accept hostname:community/operation ...
reject hostname:community/operation ...
where the wildcard character **** can stand for all hosts or all communi-
ties. A comma can be used to list multiple hosts or communities.
For example, suppose _s_n_m_p_d were to accept ggggeeeetttt and sssseeeetttt requests from the
host iiiirrrriiiissss1111 or iiiirrrriiiissss2222 with the community ssssggggiiii, and accept ggggeeeetttt requests from
any host with the community ppppuuuubbbblllliiiicccc. The /_e_t_c/_s_n_m_p_d._a_u_t_h entries would
be:
accept iris1:sgi
accept iris2:sgi
accept *:public/get
or equivalently on one line:
accept iris1,iris2:sgi *:public/get
SSSSuuuuppppppppoooorrrrtttteeeedddd SSSSeeeettttssss
_s_n_m_p_d does support SNMP sets when authorized by the above mechanism.
There are some caveats to using sets however:
The deprecated Address Translation table does not support sets. The IP
Net-to-Media table should be used instead.
The IP forwarding flag, ipForwarding, can not be set.
PPPPaaaaggggeeee 1111
SSSSNNNNMMMMPPPPDDDD((((1111MMMM)))) SSSSNNNNMMMMPPPPDDDD((((1111MMMM))))
The IP default time to live, ipDefaultTTL, can not be set.
Existing rows in the IP Route table, for which ipRouteType is not
invalid, can not be modified. A row may be removed by setting
ipRouteType to invalid as stated in RFC 1213. A row may be added by sets
to IP Route table with the new variables. Default values are added for
variables not included. The row is committed and added to the kernel
route table when the ipRouteType is set from invalid to any other state.
Existing rows in the IP Net-to-Media table, for which ipNettoMediaType is
not invalid, can not be modified. A row may be removed by setting ipNet-
toMediaType to invalid as stated in RFC 1213. A row may be added by sets
to IP Net-to-Media table with the new variables. Default values are
added for variables not included. The row is committed and added to the
kernel arp table when the ipNettoMediaType is set from invalid to any
other state.
The TCP connection state, tcpConnState, can not be set.
RRRReeeemmmmooootttteeee SSSSuuuubbbb AAAAggggeeeennnnttttssss
_s_n_m_p_d supports forwarding requests to _s_u_b _a_g_e_n_t_s. These sub agents manage
proprietary parts of the MIB. They must be able to handle the snmp proto-
col, including the ASN1 encoding and decoding of packets. The sub agents
must not use the standard snmp port 161/udp which is used by _s_n_m_p_d.
At start up _s_n_m_p_d reads the file /_e_t_c/_s_n_m_p._r_e_m_o_t_e._c_o_n_f to determine the
existence of sub agents, the parts of the MIB that they support, and the
udp port to use to communicate with them. The format of the file is:
mib-tree-identifier IP-address port timeout subagent-name
The _s_u_b_a_g_e_n_t-_n_a_m_e is optional. All other parts of the entry are required.
The fields are white-space (tab or space) separated.
An example of an entry is:
1.3.6.1.4.1.59.3 192.26.75.178 3333 3 sgi-experimental
This entry says that the sub agent supporting the mib tree rooted at
1.3.6.1.4.1.59.3 is located at IP address 192.26.75.178. It uses udp port
3333. _s_n_m_p_d-forwarded requests to the sub agent should time out after 3
seconds. The name of the agent is the sgi-experimental agent.
Since _s_n_m_p_d reads and processes lines in the file in order, multiple sub
agents can be configured that operate on nested parts of the mib. For all
agents to be seen, the more deeply nested agents should come first in the
file. For example:
1.3.6.1.4.1.59.3.26 192.26.75.1178 6666 4 sgi-exp-tv
1.3.6.1.4.1.59.3 192.26.75.178 3333 3 sgi-experimental
PPPPaaaaggggeeee 2222
SSSSNNNNMMMMPPPPDDDD((((1111MMMM)))) SSSSNNNNMMMMPPPPDDDD((((1111MMMM))))
If the above two lines were reversed in order, _s_n_m_p_d would never forward
requests to the sgi-exp-tv agent.
TTTTrrrraaaappppssss
_s_n_m_p_d issues some standard SNMP traps. At startup it reads the
/_e_t_c/_s_n_m_p_d._t_r_a_p._c_o_n_f file to determine which traps to send to which des-
tinations and what community string to use when sending traps. There are
two types of entries in the file, one for traps and destinations, and one
for the community string. The format of of the trap lines is:
trap destination-list
The trap can be either a number or a string from RFC 1157 naming the
trap. The destination list is a white space and/or comma-separated set of
IP addresses and/or host names. For example:
1 192.26.75.178, bubba
authenticationFailure 192.26.75.109
The community string entry has the format:
community name
The string in the name field is used for all traps.
To determine whether it has cold-started or warm-started, _s_n_m_p_d uses the
file /_e_t_c/_s_n_m_p_d._s_t_a_r_t.
OOOOppppttttiiiioooonnnnssss
-d _d_e_b_u_g Set debugging modes of _s_n_m_p_d. Possible values for _d_e_b_u_g
are: _d_u_m_p, which will hex dump incoming and outgoing
packets; _i_n_p_u_t, which will display decoded incoming pack-
ets; _o_u_t_p_u_t, which will display decoded outgoing packets;
and _f_o_r_e_g_r_o_u_n_d, which makes the daemon run in the fore-
ground and log messages to the standard output. The
_d_u_m_p, _i_n_p_u_t, and _o_u_t_p_u_t flags all imply the _f_o_r_e_g_r_o_u_n_d
flag.
-l _l_o_g_l_e_v_e_l Control the level of messages produced by _s_n_m_p_d. The
levels are those used by _s_y_s_l_o_g(3B). The value of
_l_o_g_l_e_v_e_l is the text string for that level. The default
_l_o_g_l_e_v_e_l is _e_r_r_o_r. To see warnings, the _l_o_g_l_e_v_e_l would
be _w_a_r_n_i_n_g. The acceptable values for _l_o_g_l_e_v_e_l can be
found in /_u_s_r/_i_n_c_l_u_d_e/_s_y_s/_s_y_s_l_o_g._h.
-u _n_a_m_e_l_i_s_t Specify a system namelist. The default is /_u_n_i_x.
PPPPaaaaggggeeee 3333
SSSSNNNNMMMMPPPPDDDD((((1111MMMM)))) SSSSNNNNMMMMPPPPDDDD((((1111MMMM))))
CAVEATS
Currently _s_n_m_p_d suports the following traps only:
coldStart warmStart authenticationFailure
FFFFIIIILLLLEEEESSSS
/usr/etc/snmpd
/etc/snmpd.auth
/etc/snmpd.data
/etc/snmpd.trap.conf
/etc/snmpd.remote.conf
/etc/snmpd.start
SSSSEEEEEEEE AAAALLLLSSSSOOOO
RFC 1157, RFC 1213
PPPPaaaaggggeeee 4444